not sure why our arity checking is less strict than 3.9. Did we get more consistent about arity when noImplicitAny is false.

better typing of this, and uglify uses their own inheritance system. I can't tell if these errors are in functions that intended to be methods, or constructor functions.

we don't understand the "instance method" pattern

var log = new EE()
log.enableProgress = function() {
  this.tracker.on(...)
}

And now with better this typing, we issue an error on 'tracker'.

better this typing, and we don't understand the pattern

Minimatch.prototype.make = make
function make() {
  if (this._made) return
}

Fixed nullability of optional parameters when using @param {unknown} [arg] bracket syntax.

another unrecognised constructor function+method pattern

Promise.config is assigned a function that contains a whole bunch of non top-level Promise.prototype.method assignments. So we don't treat a bunch of methods as constructor functions, same as the other projects in this PR.

aliased var d = this defeats this-property assignment detection =(

same, aliased var self = this

we're now checking this and the function has an incorrect @this {Element} annotation.